test: enforce PSS restricted for CI user namespace#3444
test: enforce PSS restricted for CI user namespace#3444abdullahpathan22 wants to merge 2 commits intokubeflow:masterfrom
Conversation
Overwrites the default baseline namespace label created by the profile controller exclusively during CI tests. This guarantees that test workloads simulate strict pod security standard (PSS) restricted enforcements without modifying production default baselines. Signed-off-by: abdullahpathan22 <abdullahpathan22@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
- Broaden katib triggers: tests/katib_install.sh -> tests/katib* - Broaden pipeline triggers: individual files -> tests/pipeline* - Add tests/pipeline* trigger to pipeline_run_from_notebook workflow - Replace dead experimental/security/PSS/* path (directory no longer exists) with actual test files: tests/kubeflow_profile_install.sh and tests/PSS_enable.sh across all affected workflows Note: Dashboard/profiles directory paths are intentionally kept as-is since applications/profiles/ does not exist yet on master. Those paths will be updated once the directory restructure lands. Signed-off-by: abdullahpathan22 <abdullahpathan22@users.noreply.github.com>
|
Hello @juliusvonkohout, |
What this PR does
Modifies
tests/kubeflow_profile_install.shto overwrite thekubeflow-user-example-com namespace label to
enforce: restrictedexclusively during CI testing.
Why
The Profile Controller sets
enforce: baselineby default forcustomer deployments. This change overwrites that label in CI only,
ensuring test workloads are verified under strict PSS restricted
enforcement without affecting production deployments.